--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
vendor/lxmfy/CONTRIBUTING.md c33fb39ec9b7a217f7b3d2e461cdfd3d31db74d2 (c33fb39e) Text, 1.08 KB
Contributing to LXMFy
Patches are the preferred way to contribute. Create your changes locally,
export a T383838.patch file, and send it over Reticulum.
Generating a Patch
1. Clone or fork the repository and make your changes on a branch.
2. Stage and commit your work:
T282828
git add -A
git commit -m Ta5d6ff"Short description of the change"
3. Export the commit(s) as a T383838.patch file:
T282828
T8b949e# Single most recent commit
git format-patch -1
T8b949e# Last N commits
git format-patch -N
T8b949e# All commits since a branch point
git format-patch main..HEAD
This produces one T383838.patch file per commit (e.g. T3838380001-my-change.patch).
Sending the Patch
Send the T383838.patch file as an LXMF message over Reticulum to:
T282828
7cc8d66b4f6a0e0e49d34af7f6077b5a
You can attach the file using Sideband, Meshchat, MeshchatX, or any LXMF-capable client with attachments support.
Include a brief description of what the patch does in the message body.
Patch Guidelines
• Keep patches focused on a single change or fix.
• Test your changes before exporting.
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────